🚫 🔍 [Deprecated] Trend Micro Apex One via AMA
🚫 Deprecated: This connector has been deprecated and may be removed in future versions.
🔍 Discovered: This item was discovered by scanning the solution folder but is not listed in the Solution JSON file.
Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · 📊
| Attribute | Value |
|---|---|
| Connector ID | TrendMicroApexOneAma |
| Publisher | Trend Micro |
| Used in Solutions | Trend Micro Apex One |
| Collection Method | AMA |
| Connector Definition Files | template_TrendMicro_ApexOneAMA.json |
The Trend Micro Apex One data connector provides the capability to ingest Trend Micro Apex One events into Microsoft Sentinel. Refer to Trend Micro Apex Central for more information.
Additional Information
🛠️ Device Configuration: Follow these steps to configure Apex Central. On step 6, select log format CEF.
Tables Ingested
This connector ingests data into the following tables:
| Table | Selection Criteria | Transformations | Ingestion API | Lake-Only |
|---|---|---|---|---|
CommonSecurityLog |
DeviceProduct == "Apex Central"DeviceVendor == "Trend Micro" |
✓ | ✓ | ? |
💡 Tip: Tables with Ingestion API support allow data ingestion via the Azure Monitor Data Collector API, which also enables custom transformations during ingestion.
Permissions
Resource Provider Permissions: - Workspace (Workspace): read and write permissions are required. - Keys (Workspace): read permissions to shared keys for the workspace are required. See the documentation to learn more about workspace keys.
Custom Permissions:
Setup Instructions
⚠️ Note: These instructions were automatically generated from the connector's user interface definition file using AI and may not be fully accurate. Please verify all configuration steps in the Microsoft Sentinel portal.
This data connector depends on a parser based on a Kusto Function to work as expected TMApexOneEvent which is deployed with the Microsoft Sentinel Solution. 1. Kindly follow the steps to configure the data connector
Step A. Configure the Common Event Format (CEF) via AMA data connector
Note:- CEF logs are collected only from Linux Agents
-
Navigate to Microsoft Sentinel workspace ---> configuration ---> Data connector blade .
-
Search for 'Common Event Format (CEF) via AMA' data connector and open it.
-
Check If there is no existing DCR configured to collect required facility of logs, Create a new DCR (Data Collection Rule)
Note:- It is recommended to install minimum 1.27 version of AMA agent Learn more and ensure there is no duplicate DCR as it can cause log duplicacy
-
Run the command provided in the CEF via AMA data connector page to configure the CEF collector on the machine
Step B. Forward Common Event Format (CEF) logs to Syslog agent
Follow these steps to configure Apex Central sending alerts via syslog. While configuring, on step 6, select the log format CEF.
Step C. Validate connection
Follow the instructions to validate your connectivity:
Open Log Analytics to check if the logs are received using the CommonSecurityLog schema.
It may take about 20 minutes until the connection streams data to your workspace.
If the logs are not received, run the following connectivity validation script:
-
Make sure that you have Python on your machine using the following command: python -version
-
You must have elevated permissions (sudo) on your machine - Run the following command to validate your connectivity::
sudo wget -O Sentinel_AMA_troubleshoot.py https://raw.githubusercontent.com/Azure/Azure-Sentinel/master/DataConnectors/Syslog/Sentinel_AMA_troubleshoot.py&&sudo python Sentinel_AMA_troubleshoot.py --cef
2. Secure your machine
Make sure to configure the machine's security according to your organization's security policy
Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · 📊